5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
- Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-3: Specifying Statements

The T/F Execution Conditions


The first five positions of almost every statement type are reserved for true/false execution conditions. The following is a list of the only values allowed in this group and a brief description of what they mean. See section T/F Execution Condition Values in True/False Status Indicators for a complete discussion.

Blank indicates no conditions are specified.

Tindicates a true conditional check.

Findicates a false conditional check.

- (hyphen) indicates an either true or false conditional check.

C or * indicates the presence of a temporary comment. APPX bypasses any statement that has a C or * in the first position. It is up to you to reset the indicator to one of the four values previously listed before APPX will execute the statement.

The following example demonstrates the true/false execution conditions:

   TTFF   IF   TAR RECEIPT1 POST STARTED  EQ 1

In this statement, the execution conditions TTFF requests APPX to match the corresponding values to the set of five internal true/false status indicators before executing the statement.

Application Design Manual                                         "Powered by Appx Software"

538

©2006 By APPX Software, Inc. All Rights Reserved